<HTML>
<BODY BGCOLOR="white">
<PRE>
<FONT color="green">001</FONT>    /*<a name="line.1"></a>
<FONT color="green">002</FONT>     * Licensed to the Apache Software Foundation (ASF) under one or more<a name="line.2"></a>
<FONT color="green">003</FONT>     * contributor license agreements.  See the NOTICE file distributed with<a name="line.3"></a>
<FONT color="green">004</FONT>     * this work for additional information regarding copyright ownership.<a name="line.4"></a>
<FONT color="green">005</FONT>     * The ASF licenses this file to You under the Apache License, Version 2.0<a name="line.5"></a>
<FONT color="green">006</FONT>     * (the "License"); you may not use this file except in compliance with<a name="line.6"></a>
<FONT color="green">007</FONT>     * the License.  You may obtain a copy of the License at<a name="line.7"></a>
<FONT color="green">008</FONT>     *<a name="line.8"></a>
<FONT color="green">009</FONT>     *     http://www.apache.org/licenses/LICENSE-2.0<a name="line.9"></a>
<FONT color="green">010</FONT>     *<a name="line.10"></a>
<FONT color="green">011</FONT>     * Unless required by applicable law or agreed to in writing, software<a name="line.11"></a>
<FONT color="green">012</FONT>     * distributed under the License is distributed on an "AS IS" BASIS,<a name="line.12"></a>
<FONT color="green">013</FONT>     * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.<a name="line.13"></a>
<FONT color="green">014</FONT>     * See the License for the specific language governing permissions and<a name="line.14"></a>
<FONT color="green">015</FONT>     * limitations under the License.<a name="line.15"></a>
<FONT color="green">016</FONT>     */<a name="line.16"></a>
<FONT color="green">017</FONT>    package org.apache.commons.configuration;<a name="line.17"></a>
<FONT color="green">018</FONT>    <a name="line.18"></a>
<FONT color="green">019</FONT>    import java.util.ArrayList;<a name="line.19"></a>
<FONT color="green">020</FONT>    import java.util.Collections;<a name="line.20"></a>
<FONT color="green">021</FONT>    import java.util.List;<a name="line.21"></a>
<FONT color="green">022</FONT>    <a name="line.22"></a>
<FONT color="green">023</FONT>    import org.apache.commons.configuration.interpol.ConfigurationInterpolator;<a name="line.23"></a>
<FONT color="green">024</FONT>    import org.apache.commons.configuration.reloading.Reloadable;<a name="line.24"></a>
<FONT color="green">025</FONT>    import org.apache.commons.configuration.tree.ConfigurationNode;<a name="line.25"></a>
<FONT color="green">026</FONT>    <a name="line.26"></a>
<FONT color="green">027</FONT>    /**<a name="line.27"></a>
<FONT color="green">028</FONT>     * &lt;p&gt;<a name="line.28"></a>
<FONT color="green">029</FONT>     * A specialized hierarchical configuration class that wraps a single node of<a name="line.29"></a>
<FONT color="green">030</FONT>     * its parent configuration.<a name="line.30"></a>
<FONT color="green">031</FONT>     * &lt;/p&gt;<a name="line.31"></a>
<FONT color="green">032</FONT>     * &lt;p&gt;<a name="line.32"></a>
<FONT color="green">033</FONT>     * Configurations of this type are initialized with a parent configuration and a<a name="line.33"></a>
<FONT color="green">034</FONT>     * configuration node of this configuration. This node becomes the root node of<a name="line.34"></a>
<FONT color="green">035</FONT>     * the subnode configuration. All property accessor methods are evaluated<a name="line.35"></a>
<FONT color="green">036</FONT>     * relative to this root node. A good use case for a<a name="line.36"></a>
<FONT color="green">037</FONT>     * {@code SubnodeConfiguration} is when multiple properties from a<a name="line.37"></a>
<FONT color="green">038</FONT>     * specific sub tree of the whole configuration need to be accessed. Then a<a name="line.38"></a>
<FONT color="green">039</FONT>     * {@code SubnodeConfiguration} can be created with the parent node of<a name="line.39"></a>
<FONT color="green">040</FONT>     * the affected sub tree as root node. This allows for simpler property keys and<a name="line.40"></a>
<FONT color="green">041</FONT>     * is also more efficient.<a name="line.41"></a>
<FONT color="green">042</FONT>     * &lt;/p&gt;<a name="line.42"></a>
<FONT color="green">043</FONT>     * &lt;p&gt;<a name="line.43"></a>
<FONT color="green">044</FONT>     * A subnode configuration and its parent configuration operate on the same<a name="line.44"></a>
<FONT color="green">045</FONT>     * hierarchy of configuration nodes. So if modifications are performed at the<a name="line.45"></a>
<FONT color="green">046</FONT>     * subnode configuration, these changes are immediately visible in the parent<a name="line.46"></a>
<FONT color="green">047</FONT>     * configuration. Analogously will updates of the parent configuration affect<a name="line.47"></a>
<FONT color="green">048</FONT>     * the subnode configuration if the sub tree spanned by the subnode<a name="line.48"></a>
<FONT color="green">049</FONT>     * configuration's root node is involved.<a name="line.49"></a>
<FONT color="green">050</FONT>     * &lt;/p&gt;<a name="line.50"></a>
<FONT color="green">051</FONT>     * &lt;p&gt;<a name="line.51"></a>
<FONT color="green">052</FONT>     * There are however changes at the parent configuration, which cause the<a name="line.52"></a>
<FONT color="green">053</FONT>     * subnode configuration to become detached. An example for such a change is a<a name="line.53"></a>
<FONT color="green">054</FONT>     * reload operation of a file-based configuration, which replaces all nodes of<a name="line.54"></a>
<FONT color="green">055</FONT>     * the parent configuration. The subnode configuration per default still<a name="line.55"></a>
<FONT color="green">056</FONT>     * references the old nodes. Another example are list structures: a subnode<a name="line.56"></a>
<FONT color="green">057</FONT>     * configuration can be created to point on the &lt;em&gt;i&lt;/em&gt;th element of the<a name="line.57"></a>
<FONT color="green">058</FONT>     * list. Now list elements can be added or removed, so that the list elements'<a name="line.58"></a>
<FONT color="green">059</FONT>     * indices change. In such a scenario the subnode configuration would always<a name="line.59"></a>
<FONT color="green">060</FONT>     * point to the same list element, regardless of its current index.<a name="line.60"></a>
<FONT color="green">061</FONT>     * &lt;/p&gt;<a name="line.61"></a>
<FONT color="green">062</FONT>     * &lt;p&gt;<a name="line.62"></a>
<FONT color="green">063</FONT>     * To solve these problems and make a subnode configuration aware of<a name="line.63"></a>
<FONT color="green">064</FONT>     * such structural changes of its parent, it is possible to associate a<a name="line.64"></a>
<FONT color="green">065</FONT>     * subnode configuration with a configuration key. This can be done by calling<a name="line.65"></a>
<FONT color="green">066</FONT>     * the {@code setSubnodeKey()} method. If here a key is set, the subnode<a name="line.66"></a>
<FONT color="green">067</FONT>     * configuration will evaluate it on each access, thus ensuring that it is<a name="line.67"></a>
<FONT color="green">068</FONT>     * always in sync with its parent. In this mode the subnode configuration really<a name="line.68"></a>
<FONT color="green">069</FONT>     * behaves like a live-view on its parent. The price for this is a decreased<a name="line.69"></a>
<FONT color="green">070</FONT>     * performance because now an additional evaluation has to be performed on each<a name="line.70"></a>
<FONT color="green">071</FONT>     * property access. So this mode should only be used if necessary; if for<a name="line.71"></a>
<FONT color="green">072</FONT>     * instance a subnode configuration is only used for a temporary convenient<a name="line.72"></a>
<FONT color="green">073</FONT>     * access to a complex configuration, there is no need to make it aware for<a name="line.73"></a>
<FONT color="green">074</FONT>     * structural changes of its parent. If a subnode configuration is created<a name="line.74"></a>
<FONT color="green">075</FONT>     * using the {@link HierarchicalConfiguration#configurationAt(String, boolean)<a name="line.75"></a>
<FONT color="green">076</FONT>     * configurationAt()} method of {@code HierarchicalConfiguration}<a name="line.76"></a>
<FONT color="green">077</FONT>     * (which should be the preferred way), with an additional boolean parameter it<a name="line.77"></a>
<FONT color="green">078</FONT>     * can be specified whether the resulting subnode configuration should be<a name="line.78"></a>
<FONT color="green">079</FONT>     * aware of structural changes or not. Then the configuration key will be<a name="line.79"></a>
<FONT color="green">080</FONT>     * automatically set.<a name="line.80"></a>
<FONT color="green">081</FONT>     * &lt;/p&gt;<a name="line.81"></a>
<FONT color="green">082</FONT>     * &lt;p&gt;<a name="line.82"></a>
<FONT color="green">083</FONT>     * &lt;em&gt;Note:&lt;/em&gt; At the moment support for creating a subnode configuration<a name="line.83"></a>
<FONT color="green">084</FONT>     * that is aware of structural changes of its parent from another subnode<a name="line.84"></a>
<FONT color="green">085</FONT>     * configuration (a "sub subnode configuration") is limited. This only works if<a name="line.85"></a>
<FONT color="green">086</FONT>     * &lt;ol&gt;&lt;li&gt;the subnode configuration that serves as the parent for the new<a name="line.86"></a>
<FONT color="green">087</FONT>     * subnode configuration is itself associated with a configuration key and&lt;/li&gt;<a name="line.87"></a>
<FONT color="green">088</FONT>     * &lt;li&gt;the key passed in to create the new subnode configuration is not too<a name="line.88"></a>
<FONT color="green">089</FONT>     * complex (if configuration keys are used that contain indices, a corresponding<a name="line.89"></a>
<FONT color="green">090</FONT>     * key that is valid from the parent configuration's point of view cannot be<a name="line.90"></a>
<FONT color="green">091</FONT>     * constructed).&lt;/li&gt;&lt;/ol&gt;<a name="line.91"></a>
<FONT color="green">092</FONT>     * &lt;/p&gt;<a name="line.92"></a>
<FONT color="green">093</FONT>     * &lt;p&gt;<a name="line.93"></a>
<FONT color="green">094</FONT>     * When a subnode configuration is created, it inherits the settings of its<a name="line.94"></a>
<FONT color="green">095</FONT>     * parent configuration, e.g. some flags like the<a name="line.95"></a>
<FONT color="green">096</FONT>     * {@code throwExceptionOnMissing} flag or the settings for handling list<a name="line.96"></a>
<FONT color="green">097</FONT>     * delimiters) or the expression engine. If these settings are changed later in<a name="line.97"></a>
<FONT color="green">098</FONT>     * either the subnode or the parent configuration, the changes are not visible<a name="line.98"></a>
<FONT color="green">099</FONT>     * for each other. So you could create a subnode configuration, change its<a name="line.99"></a>
<FONT color="green">100</FONT>     * expression engine without affecting the parent configuration.<a name="line.100"></a>
<FONT color="green">101</FONT>     * &lt;/p&gt;<a name="line.101"></a>
<FONT color="green">102</FONT>     * &lt;p&gt;<a name="line.102"></a>
<FONT color="green">103</FONT>     * From its purpose this class is quite similar to<a name="line.103"></a>
<FONT color="green">104</FONT>     * {@link SubsetConfiguration}. The difference is that a subset<a name="line.104"></a>
<FONT color="green">105</FONT>     * configuration of a hierarchical configuration may combine multiple<a name="line.105"></a>
<FONT color="green">106</FONT>     * configuration nodes from different sub trees of the configuration, while all<a name="line.106"></a>
<FONT color="green">107</FONT>     * nodes in a subnode configuration belong to the same sub tree. If an<a name="line.107"></a>
<FONT color="green">108</FONT>     * application can live with this limitation, it is recommended to use this<a name="line.108"></a>
<FONT color="green">109</FONT>     * class instead of {@code SubsetConfiguration} because creating a subset<a name="line.109"></a>
<FONT color="green">110</FONT>     * configuration is more expensive than creating a subnode configuration.<a name="line.110"></a>
<FONT color="green">111</FONT>     * &lt;/p&gt;<a name="line.111"></a>
<FONT color="green">112</FONT>     *<a name="line.112"></a>
<FONT color="green">113</FONT>     * @since 1.3<a name="line.113"></a>
<FONT color="green">114</FONT>     * @author &lt;a<a name="line.114"></a>
<FONT color="green">115</FONT>     * href="http://commons.apache.org/configuration/team-list.html"&gt;Commons<a name="line.115"></a>
<FONT color="green">116</FONT>     * Configuration team&lt;/a&gt;<a name="line.116"></a>
<FONT color="green">117</FONT>     * @version $Id: SubnodeConfiguration.java 1210178 2011-12-04 18:58:51Z oheger $<a name="line.117"></a>
<FONT color="green">118</FONT>     */<a name="line.118"></a>
<FONT color="green">119</FONT>    public class SubnodeConfiguration extends HierarchicalReloadableConfiguration<a name="line.119"></a>
<FONT color="green">120</FONT>    {<a name="line.120"></a>
<FONT color="green">121</FONT>        /**<a name="line.121"></a>
<FONT color="green">122</FONT>         * The serial version UID.<a name="line.122"></a>
<FONT color="green">123</FONT>         */<a name="line.123"></a>
<FONT color="green">124</FONT>        private static final long serialVersionUID = 3105734147019386480L;<a name="line.124"></a>
<FONT color="green">125</FONT>    <a name="line.125"></a>
<FONT color="green">126</FONT>        /** Stores the parent configuration. */<a name="line.126"></a>
<FONT color="green">127</FONT>        private HierarchicalConfiguration parent;<a name="line.127"></a>
<FONT color="green">128</FONT>    <a name="line.128"></a>
<FONT color="green">129</FONT>        /** Stores the key that was used to construct this configuration.*/<a name="line.129"></a>
<FONT color="green">130</FONT>        private String subnodeKey;<a name="line.130"></a>
<FONT color="green">131</FONT>    <a name="line.131"></a>
<FONT color="green">132</FONT>        /**<a name="line.132"></a>
<FONT color="green">133</FONT>         * Creates a new instance of {@code SubnodeConfiguration} and<a name="line.133"></a>
<FONT color="green">134</FONT>         * initializes it with the parent configuration and the new root node.<a name="line.134"></a>
<FONT color="green">135</FONT>         *<a name="line.135"></a>
<FONT color="green">136</FONT>         * @param parent the parent configuration<a name="line.136"></a>
<FONT color="green">137</FONT>         * @param root the root node of this subnode configuration<a name="line.137"></a>
<FONT color="green">138</FONT>         */<a name="line.138"></a>
<FONT color="green">139</FONT>        public SubnodeConfiguration(HierarchicalConfiguration parent, ConfigurationNode root)<a name="line.139"></a>
<FONT color="green">140</FONT>        {<a name="line.140"></a>
<FONT color="green">141</FONT>            super(parent instanceof Reloadable ? ((Reloadable) parent).getReloadLock() : null);<a name="line.141"></a>
<FONT color="green">142</FONT>            if (parent == null)<a name="line.142"></a>
<FONT color="green">143</FONT>            {<a name="line.143"></a>
<FONT color="green">144</FONT>                throw new IllegalArgumentException(<a name="line.144"></a>
<FONT color="green">145</FONT>                        "Parent configuration must not be null!");<a name="line.145"></a>
<FONT color="green">146</FONT>            }<a name="line.146"></a>
<FONT color="green">147</FONT>            if (root == null)<a name="line.147"></a>
<FONT color="green">148</FONT>            {<a name="line.148"></a>
<FONT color="green">149</FONT>                throw new IllegalArgumentException("Root node must not be null!");<a name="line.149"></a>
<FONT color="green">150</FONT>            }<a name="line.150"></a>
<FONT color="green">151</FONT>    <a name="line.151"></a>
<FONT color="green">152</FONT>            setRootNode(root);<a name="line.152"></a>
<FONT color="green">153</FONT>            this.parent = parent;<a name="line.153"></a>
<FONT color="green">154</FONT>            initFromParent(parent);<a name="line.154"></a>
<FONT color="green">155</FONT>        }<a name="line.155"></a>
<FONT color="green">156</FONT>    <a name="line.156"></a>
<FONT color="green">157</FONT>        /**<a name="line.157"></a>
<FONT color="green">158</FONT>         * Returns the parent configuration of this subnode configuration.<a name="line.158"></a>
<FONT color="green">159</FONT>         *<a name="line.159"></a>
<FONT color="green">160</FONT>         * @return the parent configuration<a name="line.160"></a>
<FONT color="green">161</FONT>         */<a name="line.161"></a>
<FONT color="green">162</FONT>        public HierarchicalConfiguration getParent()<a name="line.162"></a>
<FONT color="green">163</FONT>        {<a name="line.163"></a>
<FONT color="green">164</FONT>            return parent;<a name="line.164"></a>
<FONT color="green">165</FONT>        }<a name="line.165"></a>
<FONT color="green">166</FONT>    <a name="line.166"></a>
<FONT color="green">167</FONT>        /**<a name="line.167"></a>
<FONT color="green">168</FONT>         * Returns the key that was used to construct this configuration. If here a<a name="line.168"></a>
<FONT color="green">169</FONT>         * non-&lt;b&gt;null&lt;/b&gt; value is returned, the subnode configuration will<a name="line.169"></a>
<FONT color="green">170</FONT>         * always check its parent for structural changes and reconstruct itself if<a name="line.170"></a>
<FONT color="green">171</FONT>         * necessary.<a name="line.171"></a>
<FONT color="green">172</FONT>         *<a name="line.172"></a>
<FONT color="green">173</FONT>         * @return the key for selecting this configuration's root node<a name="line.173"></a>
<FONT color="green">174</FONT>         * @since 1.5<a name="line.174"></a>
<FONT color="green">175</FONT>         */<a name="line.175"></a>
<FONT color="green">176</FONT>        public String getSubnodeKey()<a name="line.176"></a>
<FONT color="green">177</FONT>        {<a name="line.177"></a>
<FONT color="green">178</FONT>            return subnodeKey;<a name="line.178"></a>
<FONT color="green">179</FONT>        }<a name="line.179"></a>
<FONT color="green">180</FONT>    <a name="line.180"></a>
<FONT color="green">181</FONT>        /**<a name="line.181"></a>
<FONT color="green">182</FONT>         * Sets the key to the root node of this subnode configuration. If here a<a name="line.182"></a>
<FONT color="green">183</FONT>         * key is set, the subnode configuration will behave like a live-view on its<a name="line.183"></a>
<FONT color="green">184</FONT>         * parent for this key. See the class comment for more details.<a name="line.184"></a>
<FONT color="green">185</FONT>         *<a name="line.185"></a>
<FONT color="green">186</FONT>         * @param subnodeKey the key used to construct this configuration<a name="line.186"></a>
<FONT color="green">187</FONT>         * @since 1.5<a name="line.187"></a>
<FONT color="green">188</FONT>         */<a name="line.188"></a>
<FONT color="green">189</FONT>        public void setSubnodeKey(String subnodeKey)<a name="line.189"></a>
<FONT color="green">190</FONT>        {<a name="line.190"></a>
<FONT color="green">191</FONT>            this.subnodeKey = subnodeKey;<a name="line.191"></a>
<FONT color="green">192</FONT>        }<a name="line.192"></a>
<FONT color="green">193</FONT>    <a name="line.193"></a>
<FONT color="green">194</FONT>        /**<a name="line.194"></a>
<FONT color="green">195</FONT>         * Returns the root node for this configuration. If a subnode key is set,<a name="line.195"></a>
<FONT color="green">196</FONT>         * this implementation re-evaluates this key to find out if this subnode<a name="line.196"></a>
<FONT color="green">197</FONT>         * configuration needs to be reconstructed. This ensures that the subnode<a name="line.197"></a>
<FONT color="green">198</FONT>         * configuration is always synchronized with its parent configuration.<a name="line.198"></a>
<FONT color="green">199</FONT>         *<a name="line.199"></a>
<FONT color="green">200</FONT>         * @return the root node of this configuration<a name="line.200"></a>
<FONT color="green">201</FONT>         * @since 1.5<a name="line.201"></a>
<FONT color="green">202</FONT>         * @see #setSubnodeKey(String)<a name="line.202"></a>
<FONT color="green">203</FONT>         */<a name="line.203"></a>
<FONT color="green">204</FONT>        @Override<a name="line.204"></a>
<FONT color="green">205</FONT>        public ConfigurationNode getRootNode()<a name="line.205"></a>
<FONT color="green">206</FONT>        {<a name="line.206"></a>
<FONT color="green">207</FONT>            if (getSubnodeKey() != null)<a name="line.207"></a>
<FONT color="green">208</FONT>            {<a name="line.208"></a>
<FONT color="green">209</FONT>                try<a name="line.209"></a>
<FONT color="green">210</FONT>                {<a name="line.210"></a>
<FONT color="green">211</FONT>                    List&lt;ConfigurationNode&gt; nodes = getParent().fetchNodeList(getSubnodeKey());<a name="line.211"></a>
<FONT color="green">212</FONT>                    if (nodes.size() != 1)<a name="line.212"></a>
<FONT color="green">213</FONT>                    {<a name="line.213"></a>
<FONT color="green">214</FONT>                        // key is invalid, so detach this subnode configuration<a name="line.214"></a>
<FONT color="green">215</FONT>                        setSubnodeKey(null);<a name="line.215"></a>
<FONT color="green">216</FONT>                    }<a name="line.216"></a>
<FONT color="green">217</FONT>                    else<a name="line.217"></a>
<FONT color="green">218</FONT>                    {<a name="line.218"></a>
<FONT color="green">219</FONT>                        ConfigurationNode currentRoot = nodes.get(0);<a name="line.219"></a>
<FONT color="green">220</FONT>                        if (currentRoot != super.getRootNode())<a name="line.220"></a>
<FONT color="green">221</FONT>                        {<a name="line.221"></a>
<FONT color="green">222</FONT>                            // the root node was changed due to a change of the<a name="line.222"></a>
<FONT color="green">223</FONT>                            // parent<a name="line.223"></a>
<FONT color="green">224</FONT>                            fireEvent(EVENT_SUBNODE_CHANGED, null, null, true);<a name="line.224"></a>
<FONT color="green">225</FONT>                            setRootNode(currentRoot);<a name="line.225"></a>
<FONT color="green">226</FONT>                            fireEvent(EVENT_SUBNODE_CHANGED, null, null, false);<a name="line.226"></a>
<FONT color="green">227</FONT>                        }<a name="line.227"></a>
<FONT color="green">228</FONT>                        return currentRoot;<a name="line.228"></a>
<FONT color="green">229</FONT>                    }<a name="line.229"></a>
<FONT color="green">230</FONT>                }<a name="line.230"></a>
<FONT color="green">231</FONT>                catch (Exception ex)<a name="line.231"></a>
<FONT color="green">232</FONT>                {<a name="line.232"></a>
<FONT color="green">233</FONT>                    // Evaluation of the key caused an exception. Probably the<a name="line.233"></a>
<FONT color="green">234</FONT>                    // expression engine has changed on the parent. Detach this<a name="line.234"></a>
<FONT color="green">235</FONT>                    // configuration, there is not much we can do about this.<a name="line.235"></a>
<FONT color="green">236</FONT>                    setSubnodeKey(null);<a name="line.236"></a>
<FONT color="green">237</FONT>                }<a name="line.237"></a>
<FONT color="green">238</FONT>            }<a name="line.238"></a>
<FONT color="green">239</FONT>    <a name="line.239"></a>
<FONT color="green">240</FONT>            return super.getRootNode(); // use stored root node<a name="line.240"></a>
<FONT color="green">241</FONT>        }<a name="line.241"></a>
<FONT color="green">242</FONT>    <a name="line.242"></a>
<FONT color="green">243</FONT>        /**<a name="line.243"></a>
<FONT color="green">244</FONT>         * Returns a hierarchical configuration object for the given sub node.<a name="line.244"></a>
<FONT color="green">245</FONT>         * This implementation will ensure that the returned<a name="line.245"></a>
<FONT color="green">246</FONT>         * {@code SubnodeConfiguration} object will have the same parent than<a name="line.246"></a>
<FONT color="green">247</FONT>         * this object.<a name="line.247"></a>
<FONT color="green">248</FONT>         *<a name="line.248"></a>
<FONT color="green">249</FONT>         * @param node the sub node, for which the configuration is to be created<a name="line.249"></a>
<FONT color="green">250</FONT>         * @return a hierarchical configuration for this sub node<a name="line.250"></a>
<FONT color="green">251</FONT>         */<a name="line.251"></a>
<FONT color="green">252</FONT>        @Override<a name="line.252"></a>
<FONT color="green">253</FONT>        protected SubnodeConfiguration createSubnodeConfiguration(ConfigurationNode node)<a name="line.253"></a>
<FONT color="green">254</FONT>        {<a name="line.254"></a>
<FONT color="green">255</FONT>            SubnodeConfiguration result = new SubnodeConfiguration(getParent(), node);<a name="line.255"></a>
<FONT color="green">256</FONT>            getParent().registerSubnodeConfiguration(result);<a name="line.256"></a>
<FONT color="green">257</FONT>            return result;<a name="line.257"></a>
<FONT color="green">258</FONT>        }<a name="line.258"></a>
<FONT color="green">259</FONT>    <a name="line.259"></a>
<FONT color="green">260</FONT>        /**<a name="line.260"></a>
<FONT color="green">261</FONT>         * Returns a hierarchical configuration object for the given sub node that<a name="line.261"></a>
<FONT color="green">262</FONT>         * is aware of structural changes of its parent. Works like the method with<a name="line.262"></a>
<FONT color="green">263</FONT>         * the same name, but also sets the subnode key for the new subnode<a name="line.263"></a>
<FONT color="green">264</FONT>         * configuration, so it can check whether the parent has been changed. This<a name="line.264"></a>
<FONT color="green">265</FONT>         * only works if this subnode configuration has itself a valid subnode key.<a name="line.265"></a>
<FONT color="green">266</FONT>         * So if a subnode configuration that should be aware of structural changes<a name="line.266"></a>
<FONT color="green">267</FONT>         * is created from an already existing subnode configuration, this subnode<a name="line.267"></a>
<FONT color="green">268</FONT>         * configuration must also be aware of such changes.<a name="line.268"></a>
<FONT color="green">269</FONT>         *<a name="line.269"></a>
<FONT color="green">270</FONT>         * @param node the sub node, for which the configuration is to be created<a name="line.270"></a>
<FONT color="green">271</FONT>         * @param subnodeKey the construction key<a name="line.271"></a>
<FONT color="green">272</FONT>         * @return a hierarchical configuration for this sub node<a name="line.272"></a>
<FONT color="green">273</FONT>         * @since 1.5<a name="line.273"></a>
<FONT color="green">274</FONT>         */<a name="line.274"></a>
<FONT color="green">275</FONT>        @Override<a name="line.275"></a>
<FONT color="green">276</FONT>        protected SubnodeConfiguration createSubnodeConfiguration(<a name="line.276"></a>
<FONT color="green">277</FONT>                ConfigurationNode node, String subnodeKey)<a name="line.277"></a>
<FONT color="green">278</FONT>        {<a name="line.278"></a>
<FONT color="green">279</FONT>            SubnodeConfiguration result = createSubnodeConfiguration(node);<a name="line.279"></a>
<FONT color="green">280</FONT>    <a name="line.280"></a>
<FONT color="green">281</FONT>            if (getSubnodeKey() != null)<a name="line.281"></a>
<FONT color="green">282</FONT>            {<a name="line.282"></a>
<FONT color="green">283</FONT>                // construct the correct subnode key<a name="line.283"></a>
<FONT color="green">284</FONT>                // determine path to root node<a name="line.284"></a>
<FONT color="green">285</FONT>                List&lt;ConfigurationNode&gt; lstPathToRoot = new ArrayList&lt;ConfigurationNode&gt;();<a name="line.285"></a>
<FONT color="green">286</FONT>                ConfigurationNode top = super.getRootNode();<a name="line.286"></a>
<FONT color="green">287</FONT>                ConfigurationNode nd = node;<a name="line.287"></a>
<FONT color="green">288</FONT>                while (nd != top)<a name="line.288"></a>
<FONT color="green">289</FONT>                {<a name="line.289"></a>
<FONT color="green">290</FONT>                    lstPathToRoot.add(nd);<a name="line.290"></a>
<FONT color="green">291</FONT>                    nd = nd.getParentNode();<a name="line.291"></a>
<FONT color="green">292</FONT>                }<a name="line.292"></a>
<FONT color="green">293</FONT>    <a name="line.293"></a>
<FONT color="green">294</FONT>                // construct the keys for the nodes on this path<a name="line.294"></a>
<FONT color="green">295</FONT>                Collections.reverse(lstPathToRoot);<a name="line.295"></a>
<FONT color="green">296</FONT>                String key = getSubnodeKey();<a name="line.296"></a>
<FONT color="green">297</FONT>                for (ConfigurationNode pathNode : lstPathToRoot)<a name="line.297"></a>
<FONT color="green">298</FONT>                {<a name="line.298"></a>
<FONT color="green">299</FONT>                    key = getParent().getExpressionEngine().nodeKey(pathNode, key);<a name="line.299"></a>
<FONT color="green">300</FONT>                }<a name="line.300"></a>
<FONT color="green">301</FONT>                result.setSubnodeKey(key);<a name="line.301"></a>
<FONT color="green">302</FONT>            }<a name="line.302"></a>
<FONT color="green">303</FONT>    <a name="line.303"></a>
<FONT color="green">304</FONT>            return result;<a name="line.304"></a>
<FONT color="green">305</FONT>        }<a name="line.305"></a>
<FONT color="green">306</FONT>    <a name="line.306"></a>
<FONT color="green">307</FONT>        /**<a name="line.307"></a>
<FONT color="green">308</FONT>         * Creates a new node. This task is delegated to the parent.<a name="line.308"></a>
<FONT color="green">309</FONT>         *<a name="line.309"></a>
<FONT color="green">310</FONT>         * @param name the node's name<a name="line.310"></a>
<FONT color="green">311</FONT>         * @return the new node<a name="line.311"></a>
<FONT color="green">312</FONT>         */<a name="line.312"></a>
<FONT color="green">313</FONT>        @Override<a name="line.313"></a>
<FONT color="green">314</FONT>        protected Node createNode(String name)<a name="line.314"></a>
<FONT color="green">315</FONT>        {<a name="line.315"></a>
<FONT color="green">316</FONT>            return getParent().createNode(name);<a name="line.316"></a>
<FONT color="green">317</FONT>        }<a name="line.317"></a>
<FONT color="green">318</FONT>    <a name="line.318"></a>
<FONT color="green">319</FONT>        /**<a name="line.319"></a>
<FONT color="green">320</FONT>         * Initializes this subnode configuration from the given parent<a name="line.320"></a>
<FONT color="green">321</FONT>         * configuration. This method is called by the constructor. It will copy<a name="line.321"></a>
<FONT color="green">322</FONT>         * many settings from the parent.<a name="line.322"></a>
<FONT color="green">323</FONT>         *<a name="line.323"></a>
<FONT color="green">324</FONT>         * @param parentConfig the parent configuration<a name="line.324"></a>
<FONT color="green">325</FONT>         */<a name="line.325"></a>
<FONT color="green">326</FONT>        protected void initFromParent(HierarchicalConfiguration parentConfig)<a name="line.326"></a>
<FONT color="green">327</FONT>        {<a name="line.327"></a>
<FONT color="green">328</FONT>            setExpressionEngine(parentConfig.getExpressionEngine());<a name="line.328"></a>
<FONT color="green">329</FONT>            setListDelimiter(parentConfig.getListDelimiter());<a name="line.329"></a>
<FONT color="green">330</FONT>            setDelimiterParsingDisabled(parentConfig.isDelimiterParsingDisabled());<a name="line.330"></a>
<FONT color="green">331</FONT>            setThrowExceptionOnMissing(parentConfig.isThrowExceptionOnMissing());<a name="line.331"></a>
<FONT color="green">332</FONT>        }<a name="line.332"></a>
<FONT color="green">333</FONT>    <a name="line.333"></a>
<FONT color="green">334</FONT>        /**<a name="line.334"></a>
<FONT color="green">335</FONT>         * Creates a ConfigurationInterpolator with a chain to the parent's<a name="line.335"></a>
<FONT color="green">336</FONT>         * interpolator.<a name="line.336"></a>
<FONT color="green">337</FONT>         *<a name="line.337"></a>
<FONT color="green">338</FONT>         * @return the new interpolator<a name="line.338"></a>
<FONT color="green">339</FONT>         */<a name="line.339"></a>
<FONT color="green">340</FONT>        @Override<a name="line.340"></a>
<FONT color="green">341</FONT>        protected ConfigurationInterpolator createInterpolator()<a name="line.341"></a>
<FONT color="green">342</FONT>        {<a name="line.342"></a>
<FONT color="green">343</FONT>            ConfigurationInterpolator interpolator = super.createInterpolator();<a name="line.343"></a>
<FONT color="green">344</FONT>            interpolator.setParentInterpolator(getParent().getInterpolator());<a name="line.344"></a>
<FONT color="green">345</FONT>            return interpolator;<a name="line.345"></a>
<FONT color="green">346</FONT>        }<a name="line.346"></a>
<FONT color="green">347</FONT>    }<a name="line.347"></a>




























































</PRE>
</BODY>
</HTML>
